1. Content
-
What’s the point ?
-
Why do we need a dedicated "flavour" ?
-
Is Papyrus ready ?
-
Workshop (meaning working!)
-
How to contribute ?
2. Before we start
|
|
Most of the screen captures in this talk are from Papyrus version 0.10.1. |
|
|
|
3. Who am I ?
-
Professor at Université de Toulouse
-
Co-founder of the SysML-France association
-
Member of the SoSyM editorial board
-
Member of the Steering Committee of the ACM/IEEE MODELS
-
Co-animator of the Ambient Systems group at IRIT
4. Format of this workshop
-
1h30
-
Few introduction slides
-
Brainstorming session
|
|
Related to this morning workshops: |
5. Why "Papyrus 4 Education" ?
-
"User" point of view
-
"Teacher" point of view
-
CEA Tech List point of view
5.1. "User" point of view
|
|
I’m addressing the industrial users here, not students. |
5.2. "Teacher" point of view
|
|
Do I need to mention I advocate open source tools? |
6. Why do we need a dedicated "flavour" ?
-
Illustration from a class experience
-
Students (beginners) problems
-
User-friendliness
6.1. Illustration from a class experience
-
The class diagram they have in mind (the one on teacher’s materials)
-
The class diagram… in practical class (after finding a pen and a sheet of paper)
-
The class diagram… they would have liked to write
class Produit {
designation
poids
}
class Fournisseur {
raisonSociale
adresse
}
Produit -- Fournisseur
-
The class diagram… in the lab (after "playing" with menus and buttons)
6.2. Students (beginners) problems
-
Palette complexity
-
UML subtilities
6.2.1. Palette complexity
6.2.2. UML subtilities
e.g., participants should be a ConnectableElement
6.3. (Eclipse) User-friendliness
— J.-M. Bruel
|
|
I know, this is a risky claim at EclipseCon :-) |
6.4. User-friendliness
-
We need to build on experiences
-
We need to build on other eclipse communities experiences
-
We need to build on other communities experiences
7. Is papyrus ready ?
-
Maturity
-
Unconference this morning: Getting started
-
Major release 1.0
-
-
Tuning/Customization possibilities
-
Unconference earlier this afternoon : DSML within Papyrus
-
Papyrus DTK (Domain Tool Kit)
-
Following illustrations
-
7.1. Additional components
7.2. Viewpoints
-
Without
-
With
7.3. CSS styles
7.4. Model explorer customization
7.5. Façades & Palettes
7.6. Customization overview
7.7. Papyrus is ready
-
Stability and maturity of Papyrus 1.0.0
-
Lots of customization mechanisms
-
Now time to disseminate
-
Explain and illustrate
-
Build customization strategies (e.g., for teaching)
-
Aggregate efforts and ideas
-
8. Brainstorming session
2 mains concerns:
-
Content
-
what are the core concepts
-
how, in which order, do we teach/address them
-
-
Tool
-
user-friendliness
-
user level/progresses integration
-
company method integration
-
9. Brainstorming session
-
Splitting in 2 main concerns?
-
Beginners in indusrty
-
Students learning UML™
-
-
Expected outputs
⇒ set of questions for critical feedbacks on Papyrus
⇒ set of questions for industrial beginners
⇒ set of questions for teachers
-
Be creative (remember welcome talk from Gaël)
-
Provoque collaboration
10. Collaborative work
11. Critical feedbacks on Papyrus
12. Industrial beginners
13. Teachers
-
Examples:
-
French O’level (STI2D option) ⇒ selection of SysML only
-
French "Classes Prépas" ⇒ all diagrams, but not all concepts
-
-
What’s the good approach?
-
"Shortening" the metamodel at first?
-
"Hiding" concepts in the palettes/explorers?
-
-
Identifying the core taught concepts
-
Identify potential targets for the form
14. How to contribute ?
-
Stay tuned ⇒ https://www.eclipse.org/papyrus/
-
Check the Papyrus forum
-
Contact project leader ⇒ Sebastien.Gerard@cea.fr
-
Contribute to the wiki ⇒ https://wiki.eclipse.org/MDT/Papyrus
15. Let’s build a community
-
In the eclipse spirit
-
open source
-
sharing experience and concerns
-
-
Beyond tool vendors race
-
we need massive adoption now
-
we need standard-based, solid tools…
-
… but we need them "sexy" and user-friendly
-